Skip to content

Fix section rendering issue#2298

Merged
hertschuh merged 1 commit intokeras-team:masterfrom
sachinprasadhs:fix_html
Feb 25, 2026
Merged

Fix section rendering issue#2298
hertschuh merged 1 commit intokeras-team:masterfrom
sachinprasadhs:fix_html

Conversation

@sachinprasadhs
Copy link
Collaborator

@sachinprasadhs sachinprasadhs commented Feb 24, 2026

Currently, when we click on any API links or sublinks, the display section starts showing the content from the middle of the document instead of the header. This is confusing and annoying for users trying to locate the correct API.

Added padding on top to make the target links directly visible and avoid hiding behind the top navigation bar which is fixed length.

Changes to
Screenshot 2026-02-24 at 3 00 47 PM

From:
image

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @sachinprasadhs, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a user interface problem where navigating to specific sections of the documentation via anchor links resulted in the target content being obscured by the fixed header. By applying a CSS property, the change ensures that when a user clicks on an internal link, the browser scrolls to a position that fully reveals the linked section, improving readability and user experience.

Highlights

  • UI Fix: Resolved an issue where clicking API links caused sections to be hidden behind the top navigation bar.
  • CSS Adjustment: Introduced scroll-padding-top to the html element to ensure target links are fully visible.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • theme/css/docs.css
    • Added scroll-padding-top to the html element.
Activity
  • No specific activity has been recorded for this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request addresses an issue where content is hidden behind the sticky navigation bar when jumping to anchors. The fix correctly uses the scroll-padding-top CSS property. My review includes a suggestion to refine the padding value to align it with the navigation bar's actual height, improving visual consistency and maintainability.

@hertschuh hertschuh merged commit 1d1ac36 into keras-team:master Feb 25, 2026
4 checks passed
@sachinprasadhs sachinprasadhs deleted the fix_html branch February 25, 2026 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants